-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Doc: Oss 339 unexpected intent policy #11982
base: main
Are you sure you want to change the base?
Doc: Oss 339 unexpected intent policy #11982
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hello @vitordiniz25 thank you for your contribution.
Unfortunately we cannot review it until you sign a contributor license.
I've just signed! :) |
`UNexpecTEDIntentPolicy` helps you review conversations and also allows your bot to react to unlikely user inputs. | ||
It is an auxiliary policy that should only be used with at least one other policy, as the only that it can trigger is the special | ||
`action_unlikely_intent` action. | ||
|
||
`UNexpecTEDIntentPolicy` has the same model architecture as `TEDPolicy`. | ||
|
||
The difference is at a task level. Instead of predicting the next probable action, this policy | ||
predicts whether the last predicted intent is a likely intent according to the training stories | ||
and conversation context. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This content is actually the same as on this page, could you please add a short sentence of how this is relevant for handling unexpected input and then link to the corresponding section in docs/docs/policies.mdx#unexpected-intent-policy
.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please also add a changelog entry of type doc
.
Proposed changes:
Status (please check what you already did):
black
(please check Readme for instructions)